Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WIP Ambiq Apollo3 support #2378

Draft
wants to merge 58 commits into
base: master
Choose a base branch
from
Draft

WIP Ambiq Apollo3 support #2378

wants to merge 58 commits into from

Conversation

thebentern
Copy link
Contributor

@thebentern thebentern commented Mar 24, 2023

No description provided.

@github-actions
Copy link
Contributor

github-actions bot commented Apr 24, 2023

🤖 Pull request artifacts

empty string

file commit
firmware-2.2.25.a7c0109.zip a7c0109

thebentern added a commit to meshtastic/artifacts that referenced this pull request Apr 24, 2023
thebentern added a commit to meshtastic/artifacts that referenced this pull request May 8, 2023
thebentern added a commit to meshtastic/artifacts that referenced this pull request Jun 12, 2023
thebentern added a commit to meshtastic/artifacts that referenced this pull request Jun 25, 2023
@caveman99
Copy link
Member

filed nigelb/platform-apollo3blue#47

thebentern added a commit to meshtastic/artifacts that referenced this pull request Jul 1, 2023
@alistair23
Copy link

I thought it might be worth pointing out that RadioLib now supports Tock

https://github.com/tock/tock/tree/master/boards/apollo3/lora_things_plus
https://github.com/jgromes/RadioLib/tree/master/examples/NonArduino/Tock

So in future it might be possible to use that for Meshtastic

thebentern added a commit to meshtastic/artifacts that referenced this pull request Jul 24, 2023
@caveman99 caveman99 marked this pull request as ready for review May 17, 2024 09:49
@caveman99 caveman99 marked this pull request as draft May 17, 2024 09:50
@fifieldt fifieldt added the hardware-support Add hardware support for new devices or modules label Sep 17, 2024
@fifieldt
Copy link
Contributor

This one's getting a bit long in the tooth. Want to keep it open?

# Conflicts:
#	arch/esp32/esp32.ini
#	arch/nrf52/nrf52.ini
#	arch/portduino/portduino.ini
#	arch/stm32/stm32.ini
#	protobufs
#	src/gps/GPS.cpp
#	src/main.cpp
#	src/mesh/StreamAPI.cpp
#	src/modules/ExternalNotificationModule.h
#	src/modules/NeighborInfoModule.cpp
@caveman99 caveman99 added the pinned Exclude from stale processing label Oct 30, 2024
@robdlg
Copy link

robdlg commented Nov 18, 2024

Since this branch pulls in platform-apollo3blue and the SparkFun Apollo3 Core, I tried adding support for the SparkFun LoRa Thing Plus - expLoRaBLE board.

I used Commit 047b8a5 from September 4, then

  1. Copied SparkFun_Thing_Plus_expLoRaBLE.json to the "boards" directory.
  2. Created the new directory "variants/LoRa_THING_PLUS_expLoRaBLE".
  3. Copied "platformio.ini" and "pins_arduino.h" from "variants/rak11720/" to the new directory.
  4. Edited "platformio.ini" for the new board but left "pins_arduino.h" alone.
  5. Copied the mbed directory from the core to the new directory.
  6. Copied core file pins.cpp to "variant.cpp" in the new directory. A one-line edit is then required.
  7. Formed the "variant.h" file in the new directory using content from core files pins.h and variant.h.

Is this a valid approach? The firmware builds successfully, but I haven't tried loading the binary onto a board.

Any insight is appreciated. Thanks.

@robdlg
Copy link

robdlg commented Dec 10, 2024

Since this branch pulls in platform-apollo3blue and the SparkFun Apollo3 Core, I tried adding support for the SparkFun LoRa Thing Plus - expLoRaBLE board.

To follow up on this comment, I did program the SparkFun LoRa Thing Plus - expLoRaBLE board with the firmware.bin file that resulted from the process I described. I was able to connect to the board using the Meshtastic CLI, and it revealed that Bluetooth was not enabled. I then went about enabling Bluetooth in the build, but when I uploaded the new firmware.bin file, the CLI would no longer connect. Reverting back to the original working firmware also results in CLI failure, and nothing I've tried enables the CLI to reconnect. I'm baffled. The board still accepts uploads so I can make LEDs blink, run a "EEPROM" test, etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hardware-support Add hardware support for new devices or modules pinned Exclude from stale processing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants